Skip to content

ci: open Release PRs as getstream-sdk-bot - #404

Open
Loschcode wants to merge 1 commit into
mainfrom
ci/release-pr-sdk-bot
Open

Loschcode wants to merge 1 commit into
mainfrom
ci/release-pr-sdk-bot

Conversation

@Loschcode

@Loschcode Loschcode commented Nov 20, 2026 •

Copy link
Copy Markdown

Why

The 2026-11-20 org hardening turned off "Allow GitHub Actions to create and approve pull requests", so release-please can no longer open Release PRs with GITHUB_TOKEN (e.g. stream-sdk-java run 44715449332). We're keeping that org setting off: it would also let GITHUB_TOKEN approve PRs, which bypasses review.

What

release-pr.yml now opens the Release PR as getstream-sdk-bot, the like the other server-side SDKs; stream-node-release-bot was uninstalled in the same cleanup:

  • mints a short-lived token from the sdk-bot environment (key stays branch-restricted there), scoped to contents + pull-requests write only
  • GITHUB_TOKEN in this job drops to contents: read (unchanged)
  • bonus: Release PRs opened by the App trigger CI, unlike GITHUB_TOKEN ones

Hotfix branches (N.x) aren't allowed by the sdk-bot environment, so there the job runs without the key on a read-only token. A push with nothing to release stays green. One with changes fails until the environment allows that branch. That path is already broken by the org setting, so this isn't a regression.

Depends on

getstream-sdk-bot being reinstalled on this repo (it was uninstalled in the same cleanup).

Verify after merge

The next push to main → Release PR opened/updated by getstream-sdk-bot[bot].

🤖 Generated with Claude Code

GITHUB_TOKEN can no longer create pull requests in the org; mint a
token from the sdk-bot environment instead of re-enabling that setting.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mogita

mogita commented Nov 20, 2026

Copy link
Copy Markdown
Contributor

Hold until getstream-sdk-bot is installed on this repo, and on GetStream/chat and GetStream/protocol. It is not installed yet: today's regen runs fail with a 404 on the App installation lookup. Merging before that just moves the failure to the release job.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants